Testing and Maintaining Integrations

After constructing the mappings, you're nearly ready to turn on your integration! Data Pull supports the ability to test the integration before you activate it, via the Tests section. Data Push allows you to manually specify a transaction to send, and can be used for testing. 

With Variance, data is joined and cached for the purposes of creating reports. To test Variance, create a sample report containing the joined keys. With a working connection, the data should align with the data from your source system.

Testing with Data Pull

Data Pull supports two modes of testing in ItemPath, testing with your connection or using manually provided data:

You can test using the connection and mapping: 

1. Leave the toggle on "Test using Connection" 
2. Test

You can test using sample JSON data: 

1. Turn off the "Test using Connection" toggle
2. Paste sample JSON containing the mapped keys from your integration
3. Test

The results of your tests will appear on the Tasks tab, with a check mark in the Test column. Select a test run to review messages associated with each part of the job associated with your integration. In the screenshot below, we see that the test failed since an order already exists with the same name:

Testing with Data Push

To test with Data Push, you can manually specify transactions to send to using the Manual Run tab before you activate your integration:

1. Find a test transaction from your Power Pick system (e.g. using the Explorer or a History report) 
2. Copy the ID and return to your Data Pull integration
3. Select the Manual Run section, then paste the transaction ID into the text box
4. Run

Results of your test will show below and will also be available in the Logs tab. See Integration Logs & Manual Send and Integration Failed attempts for more details.

Troubleshooting

By reviewing the integration specific logs, you can see any messages exchanged during the integration process and use that to troubleshoot. In addition to helping you test your integrations, these are helpful resources in case anything goes wrong with an integration after it has gone live. 

Typically errors fall into one of two categories:

1. Connection errors: a detail in the Connection or Integration settings prevent the request from successfully sending.
2. Mapping errors: either of the two services expects required data, or data in a particular format that isn't properly mapped between the two services.

ItemPath also keeps separate, full logs of every interaction with its API. These can be helpful for navigating issues with Variance.

If at any point in time you need support, don't hesitate to reach out to our support staff!

---